Message-ID: <ca824ny00VcJIE4U5z@andrew.cmu.edu>
Reply-To: space+@Andrew.CMU.EDU
From: space-request+@Andrew.CMU.EDU
To: space+@Andrew.CMU.EDU
Date: Mon,  9 Apr 90 01:44:21 -0400 (EDT)
Subject: SPACE Digest V11 #237

SPACE Digest                                     Volume 11 : Issue 237

Today's Topics:
			Re: orbit definitions
		       Orbital element program
	    Re: HST Image Status for 04/01/90 (Forwarded)
----------------------------------------------------------------------

Date: 8 Apr 90 21:38:48 GMT
From: cs.utexas.edu!uwm.edu!ogicse!zephyr.ens.tek.com!wrgate!mrloog!dant@tut.cis.ohio-state.edu  (Dan Tilque)
Subject: Re: orbit definitions

jokim@jarthur.Claremont.EDU (John H. Kim) writes:
}dant@mrloog.WR.TEK.COM (Dan Tilque) writes:
}>I'm not sure how much it's used now, but as the geostationary orbit
}>slots get filled up ...
}> ...
}>Thus it could have virtually the same longitude
}>as a comsat and without interfering with it.
}
}Not quite.  It still crosses the equator through the geostationary
}orbits.  I'd rather have a collision between two geostationary sats
}(small relative velocity) than between a geostationary and a geosynch
}(high relative velocity in the north-south direction).

Sorry, I should have said that it goes between two geostationary sats
which are at the normal longitudinal separation.  I'm not sure what the
standard separation is for comsats, but it's probably large enough for
one of the geosynch sats to slip through without high danger of
collision.


---
Dan Tilque	--	dant@mrloog.WR.TEK.COM

------------------------------

Date:     Sun, 8 Apr 90 21:40 EST
From: <K_MACART%UNHH.BITNET@vma.cc.cmu.edu>
Subject:  Orbital element program


        Does anybody out there have an orbital element program that uses
Kelso's data and runs on the IBM XT?  I use a 386 machine with that nasty DOS
everyone hates so much, and haven't seen the light and converted to UNIX.
I found one program, but it was in shellscript and C.  C is ok, but the DOS
will never like the UNIX, and visa/versa, I'm sure.  Any pointers to info
will be greatly appreciated.  Thank you.
                                        K.MacArthur (K_MACART@UNHH.BITNET)

---------------------------------------------------------------------------
  Disclaim, datclaim, what's da difference?        :)
===========================================================================

------------------------------

Date: 9 Apr 90 04:22:10 GMT
From: zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!news-server.csri.toronto.edu!utgpu!utzoo!henry@tut.cis.ohio-state.edu  (Henry Spencer)
Subject: Re: HST Image Status for 04/01/90 (Forwarded)

In article <1990Apr8.195149.6156@murdoch.acc.Virginia.EDU> gsh7w@astsun.astro.Virginia.EDU (Greg S. Hennessy) writes:
>#... call your congressperson and request that they make it a 
>#legel requirement that they make available promptly (i.e. within
>#a few weeks) samples of all images they get. 
>
>If this works it will have the effect of not being able to get
>talented scientists to create new instruments. It takes YEARS of a
>scientists career to design and build a new instruments. The scientist
>do it to get new data. If the data is available to everone...

Um, note the word "samples" in the original posting.  He's not asking
for everything to be public domain immediately.

>The best thing is to convince NASA (perhaps we should all write to
>them) that there exhists a large number of people who could use digtal
>data, and so the PR photos could be released digitally. 

This does sound like a much better idea; it gets at the key point.  We
don't really want a sample of Dr. J. Doe's data on stellar Doppler
shifts in M29; we want the flashy demo pictures, which are *already*
released, in a more useful form.  And not in some gawdawful excuse for
digital media like 7-track magtape at $1000/tape, either.
-- 
Apollo @ 8yrs: one small step.|     Henry Spencer at U of Toronto Zoology
Space station @ 8yrs:        .| uunet!attcan!utzoo!henry henry@zoo.toronto.edu

------------------------------

End of SPACE Digest V11 #237
*******************